home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Almathera Ten Pack 3: CDPD 3
/
Almathera Ten on Ten - Disc 3: CDPD3.iso
/
scope
/
001-025
/
scopedisk21
/
access14
/
update.doc
< prev
next >
Wrap
Text File
|
1995-03-18
|
10KB
|
197 lines
------------------------------------------------------------------------------
Update.doc -- Access! (C) 1987/88 By Keith Young --
Other text files in this archive:
Access!me The origional 'doc' file describing most of Access!'s
features.
Script.doc Documentation describing Acc!'s new scripting language.
Future.txt This author's ramblings about what the future may hold
for Access! (please read)
------------------------------------------------------------------------------
Time: -23:-
Date: 8/14/88
Subject: Changes/Additions to Access! Ver 1.4 since 1.3a
o File Reader -- has been _much_ improved. It now reads the file into
memory so that the scrolling can be full-speed. It is also no longer
part of the main program. It is a stand-alone program that is invoked
from Access! (it's called 'rd' and should be in your c: dir.)
'rd' may be used as a stand-alone text file-reader and should make
a handy addition to your c: directory (do _not_ 'run' it, it detaches
itself from the CLI for you. And it will _not_ work from WBench (sorry)).
Also, if Access! is up and running when you invoke it from a CLI, it
will pop up on Access!'s screen (in case you wonder where it went 8).
USAGE:
1> rd drive:directory/filename
( NOTE: there are several text files in this archive, you might want to go
ahead and finish reading them with 'rd' to get a feel for it ).
o Xmodem Bug -- Fixed... there was a bug that caused an Xmodem dload
to not recover after getting a "Checksum error..." (provided you ever
got one). This should be fixed and working fine now.
o Xmodem Send -- should be faster now... all 128 bytes are send at
one time now instead of one at a time (more improvements to come).
o File-requester -- (file) list is now sorted once the dir is read
in ( you had to click on the scroll bar to get it sorted before ). This
appears to still need a little work.
o MoreRows support -- you might have to play with the sizes a bit...
I forget what mine are set to ( cols +40, rows +16 ?). It should now
also work correctly on PAL machines ( there was a problem in CHAT
mode ) although I have no way of testing. If not, please let me know.
o No hidden chars -- on a related 'display' type problem many users
have commented that many BBSs will "clear the screen" before printing
a menu or page of text. If they do this, then start printing on the top
line, and you have one of the gadget-bars at the top; then the top line
is hidden by the gadget-bar. Now, if one of the gadget-bars is at the
top and a FF (clear screen) code is detected, I throw in a LF (line feed)
to get the cursor down one line so text is not hidden. Of course, if you
have you "page length" set incorectly, the text may (and exentually will)
still scroll up under the gadget-bar, but this extra step should help out
in most cases.
o Screen Refresh -- Any time the screen clears because of a user-
invoked function ( going in/out of CHAT mode, interlace, etc.) if there
was text on the screen, it is now re-displayed for you.
o Review Gadget -- The Review Buffer Window can now be opened by
clicking on the REVIEW gadget. (there is also a menu item in the
(temporary) 'Misc.' menu).
o Review More -- than 500 lines ( upper limit is now 800 lines of
text in the Review Buffer at one time).
o CD Support for .def file -- Access! will now (again) _first_ look
in the current directory and _then_ the S: directory for the Acc!.def
file ( please watch for future changes in format of the .def file to
avoid any problems ).
o CIS-B parsing enabled -- by default now. (the '+' in phone number
is _not_ needed to enable B protocol) You may still toggle it on/off
by hitting <L-Amiga> <b>.
o QB Block size changes -- 128 byte blocks at 300 baud, 512 byte
blocks for 1200 baud and 1024 byte blocks for anything greater than
1200 (this should speed error recovery at slower baud rates and add
only a slight bit of overhead).
o Child support -- What I'm paying my ex now...(grin, not really)
Access! will look to see if it's already 'online' when it boots and not
reset the baud rate if so, or send out the 'modem init string'.
o 'Better' 4-color mode support -- 'New Look' gadget-bars no longer
use colors that would be rendered invisable in 4-color mode. Several
other text color-choices have been changed for this reason.
o "NewCli" -- gadget now does wonderous things... first, it will look
to see if you have "ConMan" in your c: directory. If so, it assumes it's
a fairly recent version and that you are USING IT.
It then looks to see if you have "newwsh" (WShell, a commercial
Shell program also by Bill Hawes... I recommend it highly) in your c:
dir (defaults to "newcli" if not, but will be user-definable in the next
version).
Provided it finds "ConMan" it will attempt to open the newwsh(cli)
on the Acc! screen(!). If it doesn't find "conman", it _assumes_ you
don't have WShell and will try to open a plain 'ole NewCli for you on
the WB screen.
o Loadable Fonts -- You can now load in your favorite font. Actually,
you can have two seporate fonts, one for the (upper) 'Receive' window
and one for the (lower) 'Transmit' window in CHAT mode. When not in CHAT
mode, it will use the font you specify for the 'Receive' window.
A few things worth mentioning here... the 'console.device' does _not_
support 'proportional' fonts well. If the spacing (cursor position) gets
out of sync, you have probably loaded a proportional font.
Also, the System does _not_ unload fonts from memory just because I
tell it I am through using one (from within the program). They will,
however get 'flushed' if they are not being used and memory gets low. If
you have been loading several fonts trying to find one you like, you may
force this 'flush' at any time by selecting the 'Purge Memory' option (in
the 'Font' menu under 'Misc.' ).
Now that you can load in a new font, you might have an 'ibm.font'
lying around (I'll try to dig one up that I can distribute with the next
release ) that has the 'extended char set' for border graphics that many
of the IBM-run Amiga BBSs use.
To actually _see_ these graphics, you need to enable the upper half
of the char. set in the term. I'm writing this a little ahead of time and
am trying to get this version posted ASAP, so if you don't see a menu
item or a gadget somewhere on the DEFINE window to enable the upper char.
set, you can toggle it on/off by hitting <L-Amiga> <h>.
o IBM (yuk) Screen Clear -- on a related note to that mentioned above,
it seems that IBM (yuk) uses a "clear-screen" char. that the Amiga
console.device doesn't recognize. _If_ you have the extended char. set
enabled ( <L-Amiga> <h> ) there is code that will recognize this foreign
"clear screen" and it should work properly (if not, let me know).
o Phone Book -- A couple of changes/new features here... First off,
"Multi-Dial" - You can now select several numbers to be dialed, if
no connection is made the next selected number will be dialed and so on,
until you are finally connected. There is a new gadget on the Phone
Book window ( Multi-Dial ) that you select to enable this feature.
Once it is selected, you then can select/un-select whichever numbers
you'd like on the list (when it is _not_ selected, clicking on a number
the second time will dial that number as has been the case in version
1.3a; rather than un-select it).
Once you get connected (or you abort the process) and are logged off
one service, clicking on REDIAL (on one of the gadget-bars) will continue
the dialing process where it left off.
Note also, that when first building the list of numbers to dial, the
_last_ one you click on is where it will _start_ dialing in the list and
will continue sequentially from there ( 1,2,3,4...59,60,1,2...etc).
"Do-Script" - The other new gadget on the Phone Book window will let
you activate a script file (see below) connected to an individual phone
number after a connection is made.
To attach a script to a particular phone number, you place a '$' char.
as the _first_ char. of the comment feild followed _immediately_ by the
filename of the script (as shown below)...
Deep Thought NC 1-(919)-471-6436 2400 F8N1 $logon.script (Tech Info)
|--System Name---|--Phone Number---|-Baud|-Set|-----Script/Comment------|
... two things to note here (well, maybe 3 or 4)... first, if only a
filename is given (no drive or path) then the term will look for the
script in the current "System Dir:" you have specified in the DEFINE
window (the same place you have your .keys, .phone and .color files).
Second, notice that if you still want to have a comment (and still
have room for one 8) you _must_ seporate the script name and the comment
with at least one <space> as shown in the above example.
Third, enabling either the "Do-Script" or the "Multi-Dial" gadgets
will automagically enable the "Auto-Redial" gadget and thus use the
auto-dialer to determine when you are actually connected. You should keep
this in mind when writing scripts, as you will already be connected when
the script starts so the first thing your script might want to do is
send a <return> (needed by many BBSs to get logged on) then wait for some
"Password:" prompt (or whatever is appropriate).
Finally, I'm using the Comment feild on somewhat of a trial basis...
my origional thought was to have it work like the Get Keys and Get Colors
as far as determining the script name. But for many BBSs one common logon
script could be used for all (many) of them (thus reducing the number of
scripts you need to write). What I may do in a future version is a
combination of the two methods where if one was specified in the Comment
feild, over-ride the one built up from the BBS name.
o Scripts -- I am in the process of adding 'real' scripts (as opposed
to the 'psuedo scripts' that _were_ available through the macro keys).
This release has a limited (first) verson of the new scripting language
and it will be expanded in future releases. Due to the length of text
descibing the various commands and thier usage I have moved that part
of this documentation to a seporate file "Script.doc" which you should
also find in the archive.
That's it (all I can remember anyway 8).
Enjoy,
Keith
(please read "Future.txt" )